Summary

Extends pgpm docker to support additional Docker services alongside PostgreSQL via a new --include <service> flag. PostgreSQL remains the primary service started by default; additional services are opt-in only.

New capabilities:

• pgpm docker start --include minio — starts MinIO alongside Postgres
• pgpm docker stop --include minio — stops both
• pgpm docker ls — lists available services with live status (running/stopped/not created)

Architecture: A ServiceDefinition interface and ADDITIONAL_SERVICES registry make it straightforward to add more services in the future — just add an entry to the registry. Each service definition supports image, ports, env vars, commands, and named volumes.

MinIO is the first additional service (minio/minio, port 9000, default creds minioadmin/minioadmin), with a named Docker volume (minio-data) for persistent /data storage across container restarts and --recreate cycles.

All existing commands (pgpm docker start, pgpm docker stop) behave identically when --include is not specified.

Review & Testing Checklist for Human

• MinIO env var naming: The registry uses MINIO_ACCESS_KEY/MINIO_SECRET_KEY (legacy names), but the CI workflow uses MINIO_ROOT_USER/MINIO_ROOT_PASSWORD. Depending on the minio/minio image tag, the older names may be deprecated — verify these still work with minio/minio:latest
• Verify --include flag parsing with inquirerer: parseInclude handles both string and string[], but confirm that repeated flags (--include minio --include redis) actually produce an array from the arg parser rather than only keeping the last value
• End-to-end test: Run pgpm docker start --include minio locally, confirm both containers come up, then pgpm docker ls to check status output, and pgpm docker stop --include minio to tear down
• Volume persistence: After pgpm docker start --include minio, upload a file to MinIO, then pgpm docker stop --include minio && pgpm docker start --include minio and verify the file is still there

Notes

• pgpm env is intentionally not changed — no MinIO/CDN env vars are exported. Users who include MinIO will need to set CDN_ENDPOINT, AWS_ACCESS_KEY, etc. separately.
• startService duplicates the recreate/exists/running logic from startContainer. A future refactor could unify them, but keeping them separate avoids touching the existing Postgres-specific code path.
• listServices hardcodes the postgres container name as "postgres" — it won't detect a Postgres container started with a custom --name.
• No automated tests were added — this is a CLI/Docker orchestration command that would require Docker-in-Docker to test in CI.

Link to Devin session: https://app.devin.ai/sessions/44eca4b3fe5a46aaaf5c4907f0a0b600
Requested by: @pyramation